Codecov Report

Merging #1957 (0146a89) into dev (7848faa) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #1957   +/-   ##
=======================================
  Coverage   62.50%   62.50%           
=======================================
  Files          43       43           
  Lines        4902     4902           
=======================================
  Hits         3064     3064           
  Misses       1838     1838           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

I did more digging around and there should be some way to combine these: https://github.com/gitpod-io/template-gitpod-sxs-codespaces. The Codespaces environment is using the Gitpod image here.

The Gitpod base image does have a lot of things we generally don't need, but it was used for docker and java included ( full list is https://github.com/gitpod-io/workspace-images/blob/HEAD/dazzle.yaml#L3. I was wondering initially if the Gitpod image could use the devcontainers image as a base, but I can't find what's included in them.

Also what's the difference between Codespaces and Gitpod ?
Gitpod has it's own comparison https://www.gitpod.io/vs/github-codespaces. but I haven't found a simple independent review

@mahesh-panchal and @ewels got the gitpod to work with codespaces to use the same base image. Give it a test.

@nf-core-bot fix linting

what do you think about moving the GitPod files into .devcontainer so that everything is together? It shouldn't matter where those files are, right?

The .gitpod.yml's need to be where they are. What else is there to move?

I think we could do a symbolic link if you want them in the same place. But that would the best solution to deal with harcoded locations these programs are looking for information.

I think just keep the files where they are. Symlinking for the sake of grouping creates another file, and potential confusion when looking to update those files.

Ok, sounds good! Just my final outstanding 3 comments @vsmalladi then can merge 👍🏻

@ewels awesome fixed outstanding issues. Should be good.

@nf-core-bot fix linting